HTML Form Parser is a utility to parse the output of HTML forms. You would get the output mailed to you, for example, and the extension will parse all the nasty little ASCII codes for non-alpha characters into characters.
I use it in combination with Eudora. If I get just one message, I copy it from Eudora and run the Parser on it. If there are several, I save them to one text file, then open it in BBEdit and run the Parser on the file.
With the new versions, you could use Frontier or AppleScript to automatically parse any message whose subject is "Form Posted from Mozilla", or have your web server itself call a cgi script that did the parsing.
There are three versions of the parser.
• The BBEdit Extension allows you to run the parser from the Extensions menu in BBEdit. It will operate on the selection in the frontmost window (if there is a window with a selection), on the entire window's text (if there is no selection), or on the clipboard (if there is no window), and put the results in a new, untitled window.
• The XFCN allows you to parse text from within any platform that understands the XCMD/XFCN architecture. As of right now, this includes at least HyperCard, 4th Dimension, UserLand Frontier, MicroPhone Pro, and a host of others.
• The Scripting Addition version allows you to parse text from within an AppleScript. This version actually just uses the XFCN version with the XCMD Adapter Scripting Addition, which I got from the MacOS SDK CD.
This software may be distributed under the terms of the GNU General Public License (which should have been included in this distribution).
For any information on the extensions, their author, or any of PLR Software's other products and services, you may contact me at any of the adresses below.
Niel M. Bornstein
nbornstein@plr.com
PLR Software, Inc.
P.O. Box 420706
Atlanta, GA 30342-0706 USA
Revision History
1.0b3 5/8/96 - Factored out the parser() and HexToChar() functions, and put them in a separate file to make it easier to change the main() function for the different versions. First release of XFCN and Scripting Addition versions.
1.0b2 4/24/96 - Changed a number of toolbox calls to use BBEdit's callbacks. Now ignoring embedded returns and newlines - they may be mail artifacts and are certainly irrelevant to the data stream. Question: should I ask the user what to do with the result or just continue to put it in a new window?
1.0b1 4/1/96 - First publicly released version. Added clipboard if no window open. Released to MacGifts.
1.0a1 12/95 - First version tested by someone other than myself.
